Skip to content

Conversation

@yobottehg
Copy link
Contributor

@yobottehg yobottehg commented Dec 6, 2024

This pull request is for: (mark with an "x")

  • examples/*
  • modules/next
  • packages/next-drupal
  • starters/basic-starter
  • starters/graphql-starter
  • starters/pages-starter
  • Other

GitHub Issue: #811

Describe your changes

  • Added support for Next.js 15 and React 19 stable in next-drupal module.
  • Removed support for Next.js 13.
  • Adjusted all starters to use Next.js 15 and React 19 stable.

After reading through https://nextjs.org/docs/app/building-your-application/upgrading/version-15#async-request-apis-breaking-change I decided to not add the "workaround" to also support Next.js 14 because:

  1. Pages router is not affected and can totally easily be upgraded to Next.js 15
  2. App router support for next-drupal is still in beta so we can do these kind of breaking changes.
  3. Documentation says "Temporarily allow ..." Whatever that means! So better be safe.

The Changes for <Link> inside the Pages router starter is because the types did not work anymore with the pages router and react 19. I could not find a workaround. Therefore I just removed the custom "non-prefetch" link as I think this an implementation detail which is not required inside a starter / example.

@vercel
Copy link

vercel bot commented Dec 6, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-drupal-next ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 6, 2024 2:00pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
next-drupal ⬜️ Ignored (Inspect) Visit Preview Dec 6, 2024 2:00pm
next-drupal-v1-6 ⬜️ Ignored (Inspect) Visit Preview Dec 6, 2024 2:00pm

@vercel
Copy link

vercel bot commented Dec 6, 2024

@yobottehg is attempting to deploy a commit to the Chapter Three Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

@backlineint backlineint left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution @yobottehg! Provided some inline feedback, but this is most of the way there from my perspective.

Copy link
Contributor

@backlineint backlineint left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just about there! From my perspective this just needs to go back to using the custom link component (see comments inline) and also needs to have a merge conflict resolved, and then it is good to go.

@yobottehg
Copy link
Contributor Author

All requested changes addressed

Copy link
Contributor

@backlineint backlineint left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for all the work on this @yobottehg !

@backlineint backlineint merged commit 2246df1 into chapter-three:main Jan 27, 2025
1 of 4 checks passed
@backlineint backlineint mentioned this pull request Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants